NABLASOL BLOG SERIES: MOVING AWAY FROM QUICKBOOKS — PART 3 OF 3
The platform decision is made. The implementation partner is selected. Now the real work starts.
For most services companies planning a QuickBooks migration in 2026, the technical execution is not where things go wrong. The risk lives earlier in the decisions made before a single line of data moves: what to bring across, how to structure what you’re building, and what your team needs to do before the implementation partner can do their job.
This guide covers those decisions directly. It’s written for the CFO or controller who owns the migration outcome (not a vendor’s optimistic project plan), but an honest account of where QuickBooks to ERP migrations go well and where they go wrong.
You’ll come away with a clear view of the four pre-migration decisions that define implementation success, a realistic timeline, and a preparation checklist you can act on immediately.
Parts 1 and 2 of this series covered whether to migrate and how to choose a platform. This guide assumes both decisions are settled.
Decision 1: Should You Migrate Your Historical QuickBooks Data?
This is the most consequential early decision in any migration, and most companies default to “yes” without thinking it through. That default is often wrong.
The instinct makes sense: auditors ask for historical continuity, boards want year-over-year comparability, and migrating everything feels more complete. But for most services companies, that instinct leads to a longer, more expensive implementation that carries QuickBooks’s accumulated data quality issues into an expensive new platform.
There are two approaches. The right one depends on your specific audit, reporting, and regulatory requirements and not on what feels complete.
| Start Fresh at a New Fiscal Year | Migrate Historical Data |
|---|---|
| Lower implementation cost and risk. Faster go-live. Forces a clean COA design. QBO stays accessible in read-only for historical lookups. | Higher cost and complexity. Longer timeline. Data quality in QBO directly affects what arrives on the new platform. |
| Best when: your board and auditors accept a clean-break approach, and QBO can serve as the historical archive. | Required when: ongoing audit requires both years in one system, multi-year project tracking cannot be interrupted, or regulatory requirements mandate a single system of record. |
Our recommendation for most service companies: Start fresh at a new fiscal year. Keep QBO in read-only mode for historical lookups, and reconcile opening balances carefully so the new system starts with accurate numbers. It’s faster, cleaner, and lower risk. Auditors accept it more often than CFOs expect.
Make this decision before configuration begins. It shapes every phase that follows.
Decision 2: How to Redesign Your Chart of Accounts for ERP Migration?
The chart of accounts is where more QuickBooks migrations stumble than most CFOs expect. There are two instincts that both lead to the same place: an expensive platform running the wrong structure, and one approach that works.
| Approach | The Problem | What Go-Live Looks Like |
|---|---|---|
| Copy the QuickBooks chart of accounts exactly | Years of technical debt migrate with you. Unused accounts, redundant categories, and workaround structures all come across. | You’re on a new platform running the same messy structure you wanted to leave behind. Reporting is no cleaner than QBO. |
| Rebuild from scratch | No continuity with historical financials. Comparability breaks completely. | Your board cannot compare this year to last. Audit complications arise. Your implementation partner loses weeks reconstructing context. |
| Audit, clean, and restructure | Requires deliberate effort before migration begins. | You go live on a clean, well-designed structure that uses dimensions correctly. Reporting works the way you designed it to. |
How to Design Your COA for the New Platform
Modern ERP platforms use dimensions (department, client, project, service line, location) to slice financial data rather than multiplying account codes. This is a meaningful shift from how QuickBooks manages reporting through classes and locations.
Start the COA design conversation with one question: how do you want to see profitability on the new platform? By client? By project type? By service line? By team?
For eg, a 75-person professional services firm that bills across 4 practice areas would set up 4 department dimensions and report gross margin by practice rather than creating separate P&L account trees for each. The COA stays clean; the dimensions do the slicing.
The dimension structure must be designed before the COA is finalized. Getting this order wrong is one of the most common causes of reporting disappointment after go-live. Involve your accounting operations team here. They know where the workarounds live and what reports the business actually uses versus what gets produced and ignored.
Decision 3: What Happens to Your QuickBooks Integrations and Custom Automations?
If you built custom solutions on QuickBooks (AR automation, revenue recognition middleware, reconciliation workflows, AP approvals), then this is the decision most companies are least prepared for.
The reassuring answer: the work is not lost. The complete answer requires understanding what transfers, what gets rebuilt, and what gets replaced by native platform functionality.
What Transfers
The logic transfers. How your AR automation decides when to send a reminder, how your revenue recognition middleware calculates deferred revenue, how your reconciliation workflow handles exceptions; all of that institutional knowledge about how your accounting operations work is the most valuable asset going into a new platform.
From the CFO’s side, this handoff looks like a documentation exercise: your implementation team needs a clear description of each automation’s rules, triggers, and exception handling before they can replicate it. The work of figuring out your business rules has already been done. But it needs to be written down before it can be transferred.
What Gets Rebuilt
The technical integrations get rebuilt. The middleware connecting your payment processors, CRM, or billing tools to QBO needs to be re-pointed to the new platform. If your integrations were well-documented, this is a clean replatforming exercise. If they were built incrementally without documentation, the rebuild becomes an archaeology project.
What Gets Replaced
Some of what you built on QuickBooks will be replaced by native platform functionality. Revenue recognition that required custom middleware on QuickBooks may be handled natively by Sage Intacct or NetSuite. AP approval workflows that required a third-party tool on QBO may be built into the new platform.
This is a good outcome, not a cost. Native functionality is more maintainable than custom middleware. The goal of the migration is to end up with less custom code, not more.
A note on documentation: the single most useful thing you can do before handing your migration to an implementation team is to produce a clear map of every integration and automation currently connected to QuickBooks, like what it does, what triggers it, what data it moves, and what breaks if it stops. This document will save weeks of discovery time on the implementation side and reduce the risk of integrations being overlooked until after go-live.
QuickBooks Migration Timeline: What the Four Phases Actually Look Like
The honest range for a QuickBooks migration at a services company of meaningful size is 3 to 4 months from requirements sign-off to go-live. Smaller operations with cleaner data can move in 6 to 8 weeks.
Here is what is happening inside that timeline. Not a vendor’s best-case scenario, but the actual work, and who owns it.
| Phase | Timeframe | What Is Actually Happening |
|---|---|---|
| 1 | Weeks 1–4 | Requirements finalization. Chart of accounts redesign. Data audit and cleanup plan. System configuration begins with the implementation partner. Integration mapping. |
| 2 | Weeks 5–8 | Core configuration complete. Integration is underway. First test data migration run. Finance team begins reviewing configuration against real workflows. |
| 3 | Weeks 9–12 | Parallel run begins. Both QBO and the new system run simultaneously. Reconcile outputs between the two. User training. Issue log and resolution. |
| 4 | Weeks 13–16 | Go-live. Hypercare period with active implementation partner support. QBO moved to read-only archive. Post-go-live reconciliation and sign-off. |
What extends this timeline: Messy source data requiring pre-migration cleanup, unclear requirements at the start of Phase 1, scope creep on integrations, and internal bandwidth constraints. Your finance team is still running close throughout.
The parallel run: what most implementation plans don’t tell you
The parallel run, where both QuickBooks Online and the new system run simultaneously, is the most demanding phase of the migration for your internal team. Transactions are entered in both systems. Outputs are reconciled against each other. Discrepancies are investigated and resolved. All of this happens while your team is still running normal close cycles.
Plan for this before configuration begins, not when you arrive at Phase 3. Three decisions need to be made in advance:
- Who owns parallel run reconciliation – name the person, not the function
- What is the escalation path for discrepancies that can’t be resolved at the reconciliation level
- What your go-live confidence threshold is – the specific reconciliation accuracy that tells you you’re ready
Most implementations run parallel for four to six weeks. What determines where you land: the complexity of your integration layer, the volume of transactions to reconcile, and how cleanly Phase 2 configuration was executed. A well-configured system with clean data can reach go-live confidence in four weeks. A system with outstanding configuration issues or integration gaps will need six or more.
Rushing this period is how errors get discovered after go-live instead of before it.
Not sure how long your migration will take or whether your QBO setup is ready for it? We audit QuickBooks environments specifically to answer that question before implementation begins.→ Book a free discovery call
QuickBooks ERP Migration: Decisions Most CFOs Wish They Had Made Earlier
These are not implementation pitfalls. They are pre-migration decisions that determine whether the implementation has the right foundation to succeed.
1. Involve your accounting operations team before requirements are written
The people who live in the system daily catch things that CFO-level visibility misses. They know which workflows have hidden manual steps, which integrations are fragile, and which reports the business actually uses versus which ones are produced and ignored.
Their input shapes the COA design, the dimension structure, and the integration requirements in ways that protect you from expensive post-go-live surprises. Get them in the room before requirements are written.
2. Define what success looks like before configuration begins
What does a successful migration look like ninety days after go-live? Define this before the implementation begins, not after. Specific metrics (close timeline, reporting accuracy, integration reliability, team adoption rate) give you a clear target and make it easier to identify when something is off track during implementation.
Without defined success criteria, migrations drift. Scope expands, timelines slip, and the moment of ‘done’ becomes increasingly hard to identify.
3. Separate day-one integration requirements from phase two
Not every integration needs to be live on the go-live day. Trying to build every integration simultaneously is one of the most reliable ways to push a go-live date and one of the most avoidable.
Before configuration begins, run each integration through two questions:
- Can the business operate without this on day one? If yes, it’s a phase two candidate.
- Does this integration affect financial close or revenue recognition? If yes, it’s a day-one requirement regardless of complexity.
This split significantly reduces implementation complexity, gives the team a cleaner target, and protects your go-live date from scope creep on the integration layer.
4. Budget for real training and plan for change management
A powerful platform your team doesn’t know how to use delivers less value than a simpler platform they use well. Budget for hands-on training with the actual configured system before go-live, not a two-hour product walkthrough, but structured sessions where your team works through their real workflows in the new environment.
The gap between what an ERP platform can do and what a team actually uses is largest in the first 6 months. Training quality before go-live determines how quickly that gap closes.
QuickBooks Migration Preparation Checklist
This checklist covers the preparation work that belongs on your side. Six areas determine whether your implementation partner spends their engagement building your system or cleaning up what you brought them.
The items below follow a deliberate sequence. The historical period decision and COA design feed everything that follows. Complete those first before moving to data cleanup and integration documentation.
| Area | What to Resolve Before Migration Begins |
|---|---|
| Chart of Accounts | Audit your existing COA. Retire unused accounts. Design the new structure with dimensions in mind. Do not start configuration without this done. |
| Open Transactions | Reconcile all open AR, AP, and bank items in QBO. Do not migrate a backlog of unresolved transactions. |
| Customer and Vendor Data | Clean duplicates, standardize naming conventions, and remove inactive records. Data quality in QBO becomes data quality on the new platform. |
| Custom Solutions and Integrations | Document every integration and automation currently running on or connected to QBO. Map each one to a requirement on the new platform. |
| Historical Period Decision | Confirm the start date for the new system. Align with your auditors and board before configuration begins. |
| Internal Ownership | Name the internal owner for the migration. This person attends every implementation meeting and makes decisions. Without a named owner, timelines slip. |
The cleaner your QBO setup is before migration begins, the faster and cheaper the migration will be. Every hour your implementation partner spends cleaning data or figuring out how your current integrations work is an hour they are not spending on configuration. Pre-migration preparation is not overhead; it is the most cost-effective investment in the implementation.
QuickBooks Migration Preparation: What Nablasol Does Before Your Implementation Starts
Most implementation partners are excellent at building ERP systems. What they are not resourced to do and will not do at implementation rates is the preparation work that determines whether the build goes well.
What we do is the work that happens before your implementation partner engagement starts, i.e., the preparation phase that most companies underinvest in and that most migrations either skip or rush.
Our depth is in QuickBooks: how it is configured, how the data is structured, what the integrations look like, and what the accounting operations patterns mean when translated into ERP requirements.
What working with Nablasol before your migration looks like
We typically engage with service companies 4 to 12 weeks before their implementation partner kickoff. In that window, we deliver five things:
QBO environment audit. We identify data quality issues, reconciliation gaps, and structural problems in your current setup before they become implementation problems. You receive a prioritized list outlining what requires resolution and what can be carried over as-is.
Integration and automation documentation. Every integration and automation currently running on or connected to QuickBooks gets documented in the format your implementation partner needs to work from.
COA and dimension design. We design a chart of accounts and dimension structure for the new platform based on how your business actually needs to report.
Requirements definition. We help you define the requirements your implementation partner needs to configure the system correctly, covering reporting needs, workflow design, integration scope, and COA structure before configuration begins.
Operational continuity. We keep your QuickBooks-based accounting operations running cleanly during the evaluation and preparation period so you are not migrating under pressure or with a backlog of unresolved items.
Talk to the Nablasol team
A discovery call takes thirty minutes. You’ll come away with a clear picture of where your QBO environment stands, what preparation work your migration will require, and whether Nablasol is the right fit for that work.
Read the full series:
Part 1: Thinking About Moving Away From QuickBooks? Read This Before You Migrate
Part 2: When to Stop Fixing QuickBooks and Start Migrating
QuickBooks Migration: Frequently Asked Questions
What are the best practices for ensuring data integrity when migrating from QuickBooks?
Four practices protect data integrity through a QuickBooks migration: (1) reconcile all open AR, AP, and bank items before the migration begins. Do not carry an unresolved backlog into the new system; (2) run a test data migration before go-live and reconcile the outputs against QBO; (3) run both systems in parallel for four to six weeks after go-live, reconciling outputs against each other before decommissioning QBO; (4) define your go-live confidence threshold in advance. Teams that skip the parallel run discover data integrity issues after go-live, when they are expensive to fix.
How long does a QuickBooks to NetSuite migration take?
For a services company of meaningful size, plan for three to four months from requirements sign-off to go-live. That includes roughly four weeks of requirements and COA design, four weeks of configuration and integration build, four weeks of parallel run and training, and a two-week go-live and hypercare period. Smaller operations with cleaner data can move faster. What extends timelines most often are data cleanup requirements discovered late, unclear requirements at the start, and internal bandwidth constraints during the parallel run.
What is the biggest risk in a QuickBooks migration?
Unclear requirements going into configuration. This is the single most common cause of expensive rework, extended timelines, and post-go-live disappointment. A migration that starts with a detailed, validated set of requirements is substantially more likely to land on time and deliver what the business actually needs. Everything else on this list matters less than getting requirements right before configuration starts.
Can I keep using QuickBooks during the migration?
Yes, and you should. QBO remains your system of record until go-live. During the parallel run, both systems run simultaneously. After go-live, QBO moves to read-only archive status if you chose a clean-break approach. The migration does not interrupt your accounting operations, though it will add meaningful work to your team during the parallel run period.
